Web Exploitation Quiz

Q1. Transmitting a session cookie without the Secure flag risks:

JavaScript access Slow performance CSRF only Interception over any plaintext HTTP request

Q2. A man-in-the-middle position enables session hijacking by:

Allowing the attacker to read the token in transit Flooding the server Cracking the hash Changing the password

Q3. Which tool is listed for web application attacks?

Nbtstat LOIC Hunt Burp Suite

Q4. Host header injection can lead to:

TLS downgrade Directory listing Poisoned password-reset links pointing at an attacker domain Faster responses

Q5. Which is an OWASP Top 10 2021 risk?

Broken Access Control MAC Flooding Bluebugging NTP Enumeration

Q6. Which is the strongest signal for detecting a hijacked session?

A new user agent string alone Impossible travel or an abrupt change in device and location for the same token High request volume A slow request

Q7. What is SQL injection?

Backing up a database Encrypting a database Creating a DNS record Injecting code into an SQL statement

Q8. The X-Powered-By header should be removed because it:

Prevents caching Slows the response Breaks HTTP/2 Reveals the application framework and version

Q9. Which is another OWASP Top 10 2021 risk?

Rolling Code Attack ARP Spoofing Jamming Attack Server-Side Request Forgery

Q10. Which HTTP response header helps prevent clickjacking?

Content-Type Accept-Encoding X-Frame-Options Cache-Control

Q11. A web application may be accessed directly through:

ARP NTP SNMP HTML

Q12. The main purpose of a Content-Security-Policy header is to:

Cache static assets Set the character set Compress responses Restrict which sources of script, style and media a page may load

Q13. Out-of-band SQL injection uses:

A Bluetooth channel A USB channel A side channel for output Only the normal data channel

Q14. A backup file such as config.php.bak in the web root is dangerous because:

It breaks routing It wastes space The server may serve it as plain text, revealing credentials It confuses the parser

Q15. Detecting injection often starts with:

Submitting a single quote and observing whether behaviour changes Checking TLS Running a port scan Reading the source